feat: add rancher integration for airgapped environment and prime case #694
Conversation
Signed-off-by: PoAn Yang <poan.yang@suse.com>
|
|
@FrankYang0529 is there an issue with the change? |
| ## Work with prime Rancher | ||
|
|
||
| The prime Rancher uses different registry. If there is no `CATTLE_AGENT_IMAGE` environment variable, the default value uses `docker.io` as default registry whick makes the Harvester can't get correct rancher-agent image. You need to set the `CATTLE_AGENT_IMAGE` environment variable to the correct registry. |
There was a problem hiding this comment.
our doc doesn't suggest using the docker way to deploy Rancher, does Helm deployment need this?
There was a problem hiding this comment.
I have reviewed the text. Please note that I will add the Prime-specific content to the SUSE Virtualization section of the Prime doc.
| docker save rancher/rancher-agent:<version> -o rancher-agent-<version>.tar | ||
|
|
||
| # copy image tar file to the air-gapped environment |
There was a problem hiding this comment.
| # copy image tar file to the air-gapped environment | |
| # Copy the image TAR file to the air-gapped environment. |
| scp rancher-agent-<version>.tar rancher@<harvester-node-ip>:/tmp | ||
|
|
||
| # ssh to the harvester node and load the image |
There was a problem hiding this comment.
| # ssh to the harvester node and load the image | |
| # Use SSH to connect to the Harvester node, and then load the image. |
|
|
||
| When importing Harvester to an external Rancher, the rancher-agent image is decided by the external Rancher. The image may not be included in the Harvester ISO. In this case, you need to pull the rancher-agent image from the internet and load it on each node or push it to the Harvester cluster's registry. |
There was a problem hiding this comment.
| ## Integrate with External Rancher | |
| When importing Harvester to an external Rancher, the rancher-agent image is decided by the external Rancher. The image may not be included in the Harvester ISO. In this case, you need to pull the rancher-agent image from the internet and load it on each node or push it to the Harvester cluster's registry. | |
| ## Integrate with an External Rancher | |
| Rancher determines the `rancher-agent` image to be used whenever a Harvester cluster is imported. If the image is not included in the Harvester ISO, it must be pulled from the internet and loaded on each node, or pushed to the Harvester cluster's registry. |
|
|
||
| ```bash | ||
| # on a computer which can reach the internet and harvester cluster |
There was a problem hiding this comment.
| # on a computer which can reach the internet and harvester cluster | |
| # Run the following commands on a computer that can access both the internet and the Harvester cluster. |
|
|
||
| The prime Rancher uses different registry. If there is no `CATTLE_AGENT_IMAGE` environment variable, the default value uses `docker.io` as default registry whick makes the Harvester can't get correct rancher-agent image. You need to set the `CATTLE_AGENT_IMAGE` environment variable to the correct registry. | ||
|
|
||
| Example: | ||
| ```bash | ||
| docker run --privileged -d --name=rancher --restart=unless-stopped -p 8080:80 -p 6443:443 -e CATTLE_AGENT_IMAGE=<registry>/rancher/rancher-agent:v2.8.10 <registry>/rancher/rancher:v2.8.10 | ||
| ``` |
There was a problem hiding this comment.
Please remove this section. I will add it to the Prime doc. Here is the proposed text for Prime:
Rancher determines the
rancher-agentimage to be used whenever a Harvester cluster is imported. If the image is not included in the Harvester ISO, it must be pulled from the internet and loaded on each node, or pushed to the Harvester cluster's registry.Rancher Prime uses a different registry, and you must assign that registry as the value of the
CATTLE_AGENT_IMAGEenvironment variable. If you do not assign a value, Harvester is unable to obtain the correctrancher-agentimage becausedocker.iois used as the default registry.Example:
docker run --privileged -d --name=rancher --restart=unless-stopped -p 8080:80 -p 6443:443 -e CATTLE_AGENT_IMAGE=<registry>/rancher/rancher-agent:v2.8.10 <registry>/rancher/rancher:v2.8.10
No description provided.